Growth Strategy and Optimisation
Maximising growth potential with precision and purpose.
The Roadmap Trap
Why most strategic plans die in a slide deck, not in the market
The Roadmap Trap
Why most strategic plans die in a slide deck, not in the market
Every January, conference rooms around the world fill with the same ritual. A leadership team spends three days — sometimes three months — building a strategic roadmap. Priorities get ranked. Initiatives get owners. A deck gets built, usually somewhere between forty and eighty slides, and it gets presented with genuine conviction. Six months later, most of that roadmap is unrecognizable. Not because the market changed dramatically, and not because the strategy itself was wrong. It’s because the roadmap was built to survive a single moment — the approval meeting — and nothing after that.
This is the roadmap trap: mistaking a planning artifact for an execution system.
The plan was never the hard part
Strategy work has a seductive property. The planning phase is where you get to think clearly, free from the noise of daily operations. Whiteboards, frameworks, prioritization matrices — it all feels like progress, because it produces a document you can point to. But a roadmap is a snapshot of the best decision you could make with the information you had on the day you made it. The moment execution starts, new information starts arriving immediately: a competitor moves, a key hire falls through, a customer segment doesn’t respond the way the model predicted. The roadmap doesn’t have a mechanism for absorbing any of that. It just becomes progressively less accurate, one week at a time, until someone finally admits it needs to be redone.
Most organizations respond to this by scheduling more plans. Annual planning becomes quarterly planning. Quarterly becomes monthly. But adding planning cycles doesn’t solve the underlying issue — it just shortens the window before the next document goes stale. The problem was never planning frequency. It’s that planning and deciding are being treated as the same activity, when they are fundamentally different disciplines with different rhythms.
Plan quarterly. Decide daily.
Here is the distinction that matters: a strategic plan sets direction and allocates resources at a low frequency, because direction-setting requires distance, synthesis, and deliberate trade-offs that can’t happen every day. But the actual work of executing a strategy is made of hundreds of small decisions happening continuously — what to prioritize this sprint, which customer complaint signals something real, whether to renegotiate a vendor contract, how to respond when a launch underperforms in week one. Those decisions happen daily, and they are the actual mechanism through which strategy either compounds into results or quietly dissolves into good intentions.
The gap between the plan’s cadence (quarterly) and the decision’s cadence (daily) is where transformation dies. Nobody owns that gap. The roadmap tells you what matters in the abstract; it says almost nothing about how to decide, in the moment, when reality doesn’t match the plan. Most teams default to whoever’s loudest in the room, or to whatever was decided last time, or to inertia. None of those are strategy. They’re just what happens when a plan runs out of instructions.
What a decision-first approach looks like instead
The alternative isn’t a better roadmap. It’s building what we call a Decision Cadence — a lightweight, recurring structure that turns the roadmap’s priorities into a standing set of decision rights, criteria, and review points that operate at the speed the business actually moves.
Practically, that means three shifts:
First, roadmaps should specify decision criteria, not just initiatives. Instead of “launch Product X in Q3,” a decision-first roadmap specifies the conditions under which Product X ships, gets delayed, or gets killed — defined in advance, before anyone has an emotional stake in the outcome. This is the single highest-leverage change a leadership team can make, because it moves the hard thinking to a moment of clarity instead of a moment of pressure.
Second, decision rights need to be explicit and pushed down. In most organizations, the roadmap gets approved by leadership, but the actual judgment calls that determine whether it succeeds get made three or four layers below that approval, by people who were never given authority to make them — so they either escalate everything (killing speed) or make decisions no one signed off on (killing alignment). A Decision Cadence names, in writing, who can decide what without escalation, and what triggers a genuine escalation.
Third, the review rhythm has to match the decision rhythm, not the planning rhythm. Quarterly business reviews are for direction. Weekly or biweekly decision reviews — short, structured, focused only on decisions that are genuinely stuck or genuinely high-stakes — are for execution. Conflating the two means high-frequency problems wait for a low-frequency meeting to get resolved, and by the time they do, the moment to act on them has usually passed.
A short comparison
| Roadmap-first approach | Decision-first approach | |
|---|---|---|
| Primary artifact | A quarterly/annual plan document | A living set of decision criteria and rights |
| Cadence | Low-frequency (quarterly, annual) | Matched to the decision (daily, weekly) |
| What changes when reality shifts | The whole plan needs re-approval | Individual decisions get made within pre-set boundaries |
| Where judgment lives | Concentrated at leadership, revisited rarely | Distributed to the right level, exercised continuously |
| Failure mode | Plan goes stale; nobody notices until the next cycle | Bad decision gets caught and corrected quickly |
Why this matters more now than it used to
The velocity of change inside most industries has genuinely increased — not as a cliché, but as a measurable fact about how fast customer expectations, competitive moves, and available technology now shift within a single fiscal year. A planning cadence built for a slower environment doesn’t just underperform in a faster one; it actively misleads people, because it signals confidence and stability that the underlying reality no longer has. Teams keep executing against a roadmap that’s three months out of date because no one built a legitimate mechanism to update it in between.
This is also why so many transformation efforts stall in year two. Year one runs on the energy and clarity of the original plan. By year two, reality has diverged enough from that plan that teams are quietly improvising, without a shared framework for how those improvised decisions should get made — and improvisation without shared criteria produces inconsistency, which leadership then reads as “execution problems,” when it’s actually a decision architecture problem wearing an execution costume.
The real question to ask before your next planning cycle
Before building the next roadmap, it’s worth asking a different question than “what should we prioritize this year?” The better question is: “when this roadmap inevitably becomes outdated in month four, what decision-making structure will still be functioning?” If the honest answer is “we’ll call another planning meeting,” the roadmap isn’t the problem to fix. The decision architecture underneath it is.
Technology doesn’t transform businesses. Better decisions do — and better decisions require a system built to make them continuously, not a document built to describe them once.
Growth Strategy and Optimisation
Maximising growth potential with precision and purpose.
